Skip to main content
Glama

return all the docs

Retrieve all document IDs from the Document MCP Server to manage and access stored documents efficiently.

Instructions

Return a list of all the document ids.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the tool logic. It returns a list of all document IDs from the docs dictionary.
    def list_docs_id():
        return list(docs.keys())
  • mcp_server.py:46-49 (registration)
    Registration of the tool with FastMCP. Decorates the handler function with the tool name and description.
    @mcp.tool(
        name="return all the docs",
        description="Return a list of all the document ids."
    )
  • The data structure (dictionary) containing all documents that the tool returns IDs from.
    docs = {
        "deposition.md": "This deposition covers the testimony of Angela Smith, P.E.",
        "report.pdf": "The report details the state of a 20m condenser tower.",
        "financials.docx": "These financials outline the project's budget and expenditures",
        "outlook.pdf": "This document presents the projected future performance of the system",
        "plan.md": "The plan outlines the steps for the project's implementation.",
        "spec.txt": "These specifications define the technical requirements for the equipment"
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It states what the tool returns but doesn't disclose behavioral aspects like whether this is a read-only operation, potential performance implications for large document sets, pagination behavior, or authentication requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, zero waste. Every word contributes directly to understanding the tool's purpose without any redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list operation with no parameters, the description is adequate but minimal. Without annotations or output schema, it doesn't address important behavioral context like whether this returns a complete list or requires pagination, or what format the IDs are in.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description correctly indicates no parameters are needed ('all the document ids'), which aligns perfectly with the empty input schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('return') and resource ('list of all the document ids'), making the purpose unambiguous. It doesn't explicitly differentiate from sibling tools like 'read_doc_contents', but the focus on IDs rather than contents provides implicit distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like 'read_doc_contents' or 'edit_document'. The description implies it returns IDs only, but doesn't state when that's preferable over fetching full document contents.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mparth14/MCP-anthropic'

If you have feedback or need assistance with the MCP directory API, please join our Discord server